Skip to main content
Version: V12

How to Mask Visitor IP Address and User Agent in VIDIZMO

VIDIZMO records each visitor's IP address and user agent (browser and operating system information) against portal activity such as sign-ins, content views, and audit events. If your organization's privacy or compliance policy limits the collection of these fields, you can mask them for the whole portal from Control Panel > Security > Portal Masking.

This guide explains how masking works, how to turn it on for each field, and what changes once a field is masked.

How masking works​

Masking is applied per field — you control the visitor IP address and the user agent independently. Both fields are collected by default, so existing portals are unaffected until an administrator opts out.

Masking has two layers that you set separately for each field:

  • Layer 1 — Mask the stored value. When you mask a field, VIDIZMO stops recording its real value for new activity and stores a masked value instead. You choose how the value is masked (see Mask functions below).
  • Layer 2 — Disable processing (optional). Masking the stored value alone keeps the features that use the field working on the real value. The optional Also disable sub-option additionally stops those features from using the field for new activity.

Note: Masking applies going forward only. Values that were already collected are not changed or removed.

Mask functions​

When you mask a field, select an option under How to mask to decide what gets stored:

FunctionWhat it stores
Drop — record nothing (store blank)Stores a blank value.
Truncate (recommended) — coarsen the valueStores a coarsened version of the value. This is the default.
Hash — irreversible per-tenant tokenStores an irreversible token that cannot be turned back into the original value.
Static — replace with a fixed valueStores a fixed replacement value that you type in the Replacement value field.

Prerequisites​

  • You must have permission to manage the portal's security settings.
  • Decide which fields your organization needs to mask and how each should be masked before you begin.

Steps to mask a field​

Step 1: Open the Portal Masking page​

  1. Go to Control Panel.
  2. Under Security, select Portal Masking.

Step 2: Mask the visitor IP address​

  1. Select Mask visitor IP addresses (stop collecting).
  2. Under How to mask, choose a mask function. Truncate (recommended) is selected by default.
  3. If you chose Static — replace with a fixed value, type the value to store in the Replacement value field.
  4. To also stop the features that use the IP address, select Also disable IP-based geo-location and access restriction. Leave this clear to keep those features running on the real value.

Step 3: Mask the user agent​

  1. Select Mask visitor user agent / browser information (stop collecting).
  2. Under How to mask, choose a mask function.
  3. If you chose Static — replace with a fixed value, type the value to store in the Replacement value field.
  4. To also stop the features that use the user agent, select Also disable User Agent–based analytics and bot detection.

Note: When you disable processing for a field, the page shows a warning explaining that the dependent features stop for new activity and that masking the stored value alone would keep them working. Previously collected data is not affected.

Step 4: Save​

  1. Select Update.

Your masking settings take effect for activity recorded after you save.

What changes while a field is masked​

Masking the stored value (Layer 1) affects what gets recorded or shared:

  • Audit, activity, and sign-in records. New records store the masked value instead of the real IP address or user agent. The audit log — including its PDF and CSV exports — shows the masked IP in place of the real one. Previously recorded values are unchanged.
  • Live meetings (IP). While IP masking is on, the IP shared with other participants is the masked value (for example, a truncated IP, or blank when you choose Drop) — never the real IP. This follows the mask function you selected and applies whether or not Also disable is on.

Disabling processing (Layer 2) additionally stops the features that use the field for new activity. These keep working while only masking is on:

  • Geo-location restriction and IP blacklisting (IP). These keep enforcing on the real IP address while only masking is on. They stop enforcing for new requests when you select Also disable IP-based geo-location and access restriction. Your saved restriction rules are preserved either way.
  • Demographics and location reports (IP). New location and demographics data stops accruing when IP processing is disabled. Existing data continues to display, and the report shows a notice that IP-based location is disabled and no new location data is being collected.
  • Browser, OS, and device analytics, and bot detection (User Agent). These stop using the user agent for new activity when you select Also disable User Agent–based analytics and bot detection, so no new browser, OS, or device breakdowns accrue while that option is on.

Key considerations​

  • Masking is off by default. Existing portals continue to collect both fields until an administrator turns masking on.
  • Masking applies to new activity only. It does not scrub or alter values that were recorded before masking was turned on.
  • The Replacement value field is used only by the Static mask function. Other functions ignore it.
  • To resume collecting a field, clear its mask toggle and select Update. Geo-location restriction, analytics, and other dependent features resume on the real value.

See Also​

Did you find this article helpful?